Decryption of secure sockets layer sessions having enabled perfect forward secrecy using a diffie-hellman key exchange

ABSTRACT

A device may receive client cipher information, associated with initiating a secure session, identifying at least one key exchange cipher supported by a client device associated with the secure session. The device may determine, based on the client cipher information, that a Diffie-Hellman key exchange is to be used to establish the secure session. The device may determine whether a server device, associated with the secure session, supports use of the Diffie-Hellman key exchange. The device may manage establishment of the secure session using a first decryption technique based on determining that the server device does not support the use of the Diffie-Hellman key exchange, or manage establishment of the secure session using a second decryption technique based on determining that the server device supports the use of the Diffie-Hellman key exchange or being unable to determine whether the server device supports the use of the Diffie-Hellman key exchange.

RELATED APPLICATIONS

This application relates to U.S. patent application Ser. No. 14/751,332,filed on Jun. 26, 2015, and U.S. patent application Ser. No. 14/751,409,filed on Jun. 26, 2015, the contents of which are incorporated byreference herein in their entirety.

BACKGROUND

A Diffie-Hellman key exchange may be used for securely exchangingcryptographic keys over a public network. The Diffie-Hellman keyexchange allows two devices that have no prior knowledge of each otherto jointly establish a shared secret key over the public channel. Theshared secret key may then be used to encrypt a session key and/ortraffic associated with a symmetric key cipher.

SUMMARY

According to some possible implementations, a method may includereceiving, by a device, client cipher information associated withinitiating a secure session, where the client cipher information mayidentify one or more key exchange ciphers supported by a client deviceassociated with the secure session; determining, by the device and basedon the client cipher information, that the client device prefers use ofa Diffie-Hellman key exchange to establish the secure session;determining, by the device, whether a server device, associated with thesecure session, supports the use of the Diffie-Hellman key exchange toestablish the secure session; and selectively establishing, by thedevice, the secure session using a first decryption technique or asecond decryption technique based on determining whether the serverdevice supports the use of the Diffie-Hellman key exchange, where thefirst decryption technique may be different from the second decryptiontechnique.

According to some possible implementations, a device may include one ormore processors to: receive client cipher information associated withinitiating a secure session, where the client cipher information mayidentify at least one key exchange cipher supported by a client deviceassociated with the secure session; determine, based on the clientcipher information, that a Diffie-Hellman key exchange is to be used toestablish the secure session; determine whether a server device,associated with the secure session, supports use of the Diffie-Hellmankey exchange to establish the secure session; and manage establishmentof the secure session using a first decryption technique based ondetermining that the server device does not support the use of theDiffie-Hellman key exchange; manage establishment of the secure sessionusing a second decryption technique based on determining that the serverdevice supports the use of the Diffie-Hellman key exchange; or manageestablishment of the secure session using the second decryptiontechnique based on being unable to determine whether the server devicesupports the use of the Diffie-Hellman key exchange.

According to some possible implementations, a computer-readable mediummay store instructions that, when executed by one or more processors,cause the one or more processors to: receive client cipher informationassociated with initiating a secure sockets layer session or a transportlayer security session (SSL/TLS session), where the client cipherinformation may identify a set of key exchange ciphers supported by aclient device associated with the SSL/TLS session; determine, based onthe client cipher information, that a Diffie-Hellman key exchange is tobe used to establish of the SSL/TLS session; determine whether a serverdevice, associated with the SSL/TLS session, supports use of theDiffie-Hellman key exchange to establish of the SSL/TLS session; andestablish the SSL/TLS session using a SSL forward proxy technique basedon determining that the server device supports the use of theDiffie-Hellman key exchange or based on being unable to determinewhether the server device supports the use of the Diffie-Hellman keyexchange; or establish the SSL/TLS session using a SSL inboundinspection technique based on determining that the server device doesnot support the use of the Diffie-Hellman key exchange.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented;

FIG. 3 is a diagram showing example functional components of thesecurity device of FIG. 2;

FIG. 4 is a diagram of example components of one or more devices of FIG.2;

FIG. 5 is a flow chart of an example process for determining whether aDiffie-Hellman key exchange may be used to establish a secure session,and establishing the secure session accordingly;

FIG. 6 is a diagram of an example implementation relating to the exampleprocess shown in FIG. 5;

FIG. 7 is a diagram of an additional example implementation relating tothe example process shown in FIG. 5; and

FIG. 8 is a diagram of another example implementation relating to theexample process shown in FIG. 5.

DETAILED DESCRIPTION

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

A security device may host a firewall associated with managing (e.g.,inspecting, processing, monitoring, etc.) traffic provided by and/ordestined for a client device and/or a server device. In someimplementations, the client device may be capable of initiating a securesession with the server device to allow the traffic to be encrypted(e.g., for security purposes, for privacy purposes, etc.). For example,the client device may be capable of initiating a SSL/TLS session or aTLS session (herein referred to as a SSL/TLS session) with the serverdevice. As such, the security device may need to be capable ofdecrypting the encrypted traffic in order to inspect the traffic andenforce a security policy associated with the secure session

In some implementations, the security device may be capable of usingmultiple, different types of decryption techniques to manage theencrypted traffic associated with the secure session. For example, thesecurity device may be capable of using a SSL forward proxy technique inorder to manage encrypted traffic associated with a secure session. Whenimplementing the SSL forward proxy technique, the security device maysplit the secure session into two parts and act as a man-in-the-middle(e.g., between the client device and the server device). Using a RSA keyexchange, the security device may receive a server certificate, providedby the server device, and may forward a copy of the server certificateto the client device after replacing a server public key, associatedwith the server certificate, with a public key associated with thesecurity device. Here, the security device may also sign the servercertificate with certificate authority details associated with thesecurity device.

The client device may generate a master key for the secure session andencrypt the master key using the public key in the server certificate.Since the security device has replaced the server public key with thesecurity public key, the security device may have access to acorresponding private security key and may decrypt the master key forthe session. As such, the security device may have access to the sessionkey and may be capable of decrypting encrypted traffic associated withthe secure session. The SSL forward proxy technique may be implementedin a case where the server device is not known to the security device.Similarly, the security device may be capable of using a reverse proxytechnique to manage the encrypted traffic (e.g., in order to offload SSLprocessing from the server device), where the session between thereverse proxy and the server device may or may not be a SSL/TLS session.

As another example, the security device may be capable of using a SSLinbound inspection technique in order to manage encrypted trafficassociated with the secure session. In this case, the security devicemay store or have access to a server private key associated with theserver device and corresponding to the server public key. Here, when theclient device encrypts the session key using the server public key for aRSA key exchange, the security device may decrypt the encrypted sessionkey using the server private key. The security device may then decrypttraffic using the session key without acting as a man-in-the-middle ofthe SSL/TLS session. The SSL inbound inspection technique may beimplemented in a case where the server device is known to the securitydevice, and may be considerably faster than the SSL forward proxytechnique when managing the encrypted traffic. Using the SSL inboundinspection technique, the security device may not participate in anSSL/TLS handshake associated with establishing the SSL/TLS session.Rather, parameters associated with the SSL/TLS session may be negotiatedbetween the client device and the server device, and the security devicemay have access to a server private key and be capable of decryptingtraffic associated with the SSL/TLS session.

In some cases, the client device and the server device may participatein a RSA key exchange, as described above, where, in the case of SSLinbound inspection, the client device encrypts a session key using aserver public key, or, in the case of SSL forward proxy, the clientdevice encrypts the session key using a security device public key.However, such RSA key exchanges may be secure only while thecorresponding private key is uncompromised since the session key may bedetermined using the server private key in both SSL inbound inspectionand SSL forward proxy scenarios. For example, if the correspondingprivate key is stolen by a third party at a later time, any SSL/TLSsessions recorded by the third party may be accessed using thecorresponding private key (e.g., by determining session keys,corresponding to the SSL/TLS sessions, using the corresponding privatekey).

In some implementations, this problem may be alleviated with use of aDiffie-Hellman key exchange, whereby the client device and the serverdevice establish a shared secret key to be used to encrypt the sessionkey. The Diffie-Hellman key exchange may result in a different sharedsecret key for each session (e.g., thus enabling perfect forwardsecrecy). Thus, even if a shared secret key is compromised at a latertime, only the SSL/TLS session corresponding to the shared secret keymay be accessed. However, in such a case, the security device may nothave access to the shared secret key (e.g., since the shared secret keyis not provided by the client device or the server device at any time),and thus may not be capable of determining the session key. As such, thesecurity device may be unable to decrypt the encrypted traffic and/ormanage, inspect, process, or monitor the encrypted traffic.

Although, in a case where the security device is configured to use theSSL forward proxy technique, the security device may receive, from theclient device a request to establish an SSL/TLS session using a DiffieHellman key exchange. The client device may indicate such a request byhaving Diffie Hellman key exchange ciphers at a higher priority than aRSA key exchange. An SSL forward proxy module of the security device maytry to switch establishment of the SSL/TLS session to using aDiffie-Hellman key exchange. For example, the security device maygenerate an interdicted certificate by replacing a server public key onthe server certificate with a security device configured public key(security public key), and signing the server certificate withcertificate authority details associated with the security device. Thesecurity device may then generate Diffie-Hellman parameters needed tocreate a session key, and use a private key, corresponding to thesecurity public key on the interdicted certificate, to sign theDiffie-Hellman parameters. Here, the client device may authenticate theDiffie-Hellman parameters by verifying the signature using the securitypublic key on the interdicted certificate, and may continue withgenerating the session key and establishing the SSL/TLS session. In thisexample, the SSL forward proxy module may similarly initiate aconnection with the server device with Diffie-Hellman key exchangeciphers at higher priority. The server device may opt for Diffie-Hellmankey exchange or downgrade the request to a RSA key exchange, and the SSLforward proxy module may continue session establishment as indicated bythe server device.

In other words, the security device may establish a first shared secretkey with the client device and a second shared secret key with theserver device. Therefore, the security device may be capable ofdecrypting the encrypted session key provided by the client device,since the client device may encrypt the session key using the firstshared secret key. Here, the security device may generate anothersession key and encrypt the other session key with a second shared keyand provide the encrypted other session key to server device. Thus, byacting as a man-in-the-middle using the SSL forward proxy technique, thesecurity device may be capable of determining the session key anddecrypting the encrypted traffic associated with the SSL/TLS session.

However, in a case where the security device uses the SSL inboundinspection technique, the security device may not be capable ofdecrypting the encrypted session key since, for example, the securitydevice does not act as a man-in-the-middle between the client device andthe server device, and the Diffie-Hellman key exchange may take placewithout intervention by the security device. As such, the securitydevice may not have access to the shared secret key, may be unable todecrypt the encrypted session key and, thus, may not decrypt theencrypted traffic associated with the SSL/TLS session. In this case, thesecurity device may either drop the SSL/TLS session or allow theencrypted traffic to pass uninspected, both of which may be undesirableresults in terms of customer experience, connection reliability,security, or the like.

Implementations described herein may allow a security device todetermine whether a secure session is to be established using aDiffie-Hellman key exchange and, based on the determination, identify adecryption technique to be used for establishing and managing the securesession. This may allow the security device to operate at an improvedlevel by using the SSL inbound inspection technique when possible, andswitching to the SSL forward proxy technique when needed.

FIG. 1 is a diagram of an overview of an example implementation 100described herein. For the purposes of example implementation 100, assumethat a security device is positioned between a client device and aserver device, and that the security device hosts a firewall associatedwith managing, inspecting, processing, monitoring, or the like, trafficprovided by and/or destined for a client device.

As shown in FIG. 1, and by reference number 110, the client device mayreceive an indication to initiate a SSL/TLS session with server device.As shown by reference number 120, the client device may provide amessage associated with initiating the SSL/TLS session with the serverdevice. As shown, the message may include client cipher information,associated with the client device, and a server indicator associatedwith the server device. In some implementations, the client cipherinformation may include information that identifies one or more keyexchange ciphers, supported by the client device, that may be used toestablish the SSL/TLS session, such as a RSA key exchange, aDiffie-Hellman key exchange, an elliptic curve Diffie-Hellman keyexchange, or the like. As a particular example, in some implementations,the message may include a client hello message that includes a supportedcipher list for the client device, a TLS server name indicationextension that includes a hostname associated with the server device,other information associated with an SSL handshake, or the like.

For the purposes of FIG. 1, assume that the security device isconfigured to inspect traffic provided by the client device, and analyzemessages associated with initiating SSL/TLS sessions provided by theclient device. Based on analyzing the message, the security device may(e.g., based on information included in a packet associated with themessage) match a firewall rule to the client device, and may determine adecryption profile with which the firewall rule is associated. In someimplementations, the decryption profile may include information thatidentifies a decryption technique that is to be used to manage encryptedtraffic for the SSL/TLS session, such as a SSL inbound inspectiontechnique or a SSL forward proxy technique. As shown by reference number130, assume that the decryption profile indicates that the securitydevice is to use the SSL inbound inspection technique to manage theencrypted traffic associated with the SSL/TLS session.

As shown by reference number 140, a SSL inbound inspection module of thesecurity device may determine, based on the client cipher informationincluded in the message, that the client device has indicated apreference to use a Diffie-Hellman key exchange to establish the SSL/TLSsession. As shown by reference number 150, after determining that theclient device has indicated the preference for use of the Diffie-Hellmankey exchange, the security device may perform a server cipher preferencecache lookup, using the server indicator, to determine whether theserver device supports the use of Diffie-Hellman key exchanges toestablish SSL/TLS sessions. In some implementations, the server cipherpreference cache may include information indicating whether the serverdevice supports Diffie-Hellman key exchanges, key exchange cipherpriority information associated with the server device, or the like. Forthe purposes of example implementation 100, assume that the servercipher preference cache includes information indicating that the serverdevice supports Diffie-Hellman key exchanges.

As shown by reference number 160, based on determining that the serverdevice supports Diffie-Hellman key exchanges, the SSL inbound inspectionmodule may hand over establishment and management of the SSL/TLS sessionto a SSL forward proxy module of the security device. As shown byreference number 170, the SSL forward proxy module may proceed withestablishing the SSL/TLS session using the Diffie-Hellman key exchange(e.g., such that the security device may determine a session key in themanner described above), and may manage the encrypted traffic for theSSL/TLS session using the SSL forward proxy technique, accordingly.

In this way, a security device may determine whether a secure session isto be established using a Diffie-Hellman key exchange and, based on thedetermination, may identify a decryption technique to be used forestablishing and managing the secure session. This may allow thesecurity device to decrypt encrypted traffic following a Diffie-Hellmankey exchange, even when the security device initially determines thatthe SSL/TLS session is to be managed using a SSL inbound inspectiontechnique. Moreover, this may allow the SSL inbound inspection techniqueto be used when possible, thereby reducing an amount of computingresources consumed by the security device (e.g., since the securitydevice may consume more computing resources during establishment of theSSL/TLS session using the SSL forward proxy technique as compared to theSSL inbound inspection technique).

Notably, while systems and/or methods described herein may be describedin the context of using the SSL forward proxy technique or the SSLinbound inspection technique, in some implementations, one or more otherdecryption techniques may be used. For example, the systems and/ormethods described herein may be applied to a set of decryptiontechniques that includes a first decryption technique that may beimplemented when the client device or the server device does not supportDiffie-Hellman key exchanges, and a second decryption technique that maybe implemented when the client device and the server device supportDiffie-Hellman key exchanges.

Additionally, while the systems and/or methods described herein may bedescribed in the context of a SSL/TLS session, in some implementations,the systems and/or methods may be used in association with another typeof secure session via which traffic, encrypted with a session key, issent and/or received by a client device and/or a server device.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.2, environment 200 may include a client device 210, a security device220, a server device 230, and a network 240. Devices of environment 200may interconnect via wired connections, wireless connections, or acombination of wired and wireless connections.

Client device 210 may include one or more devices capable ofcommunicating with other devices, such as security device 220 and/orserver device 230, via network 240. For example, client device 210 mayinclude a computing device, such as a laptop computer, a tabletcomputer, a handheld computer, a desktop computer, a mobile phone (e.g.,a smart phone, a radiotelephone, etc.), or a similar device. In someimplementations, client device 210 may be capable of initiating a securesession with server device 230, such as a SSL/TLS session. In someimplementations, client device 210 may be capable of participating in aDiffie-Hellman key exchange to establish the SSL/TLS session with serverdevice 230.

Security device 220 may include one or more devices capable of managing,inspecting, processing, and/or monitoring, traffic provided by and/ordestined for client device 210 and associated with a secure sessionbetween client device 210 and another device, such as a SSL/TLS sessionbetween client device 210 and server device 230. For example, securitydevice 220 may include a computing device, such as a server device or agroup of server devices. Additionally, or alternatively, security device220 may be implemented within a cloud computing network using one ormore virtual machines. In some implementations, security device 220 mayhost a firewall associated with client device 210 and/or may store orhave access to a decryption profile associated with one or more firewallrules corresponding to the firewall.

In some implementations, security device 220 may be capable of usingmultiple, different decryption techniques to manage encrypted trafficassociated with the SSL/TLS session, such as a SSL forward proxytechnique, a SSL inbound inspection technique, or the like.Additionally, or alternatively, security device 220 may store or haveaccess to a decryption profile associated with determining a decryptiontechnique to be used to manage the encrypted traffic. In someimplementations, security device 220 may store or have access to aserver cipher preference cache associated with one or more serverdevices 230. Additional, details regarding security device 220 aredescribed below with regard to FIG. 3.

In some implementations, security device 220 may include one or moredevices capable of processing and/or transferring traffic associatedwith client device 210. For example, security device 220 may include anetwork device, such as a reverse proxy, a server (e.g., a proxyserver), a traffic transfer device, a router, a load balancer, or thelike.

In some implementations, security device 220 may be used in connectionwith a single client device 210 or a group of client devices 210 (e.g.,included in a client network). Communications may be routed throughsecurity device 220 to reach client device(s) 210. For example, securitydevice 220 may be positioned within a network as a gateway to a clientnetwork that includes one or more client devices 210. In someimplementations, security device 220 may be used in connection with asingle server device 230 or a group of server devices 230 (e.g., a datacenter). Communications may be routed through security device 220 toreach the one or more server devices 230. For example, security device220 may be positioned within a network as a gateway to a private networkthat includes one or more server devices 230.

Server device 230 may include one or more devices capable of receiving,generating, storing, and/or providing traffic to and/or from securitydevice 220 and/or client device 210. For example, server device 230 mayinclude a computing device, such as a server (e.g., an applicationserver, a content server, a host server, a web server, etc.) or acollection of servers. In some implementations, server device 230 may becapable of participating in a Diffie-Hellman key exchange to establish aSSL/TLS session with client device 210.

Network 240 may include one or more wired and/or wireless networks thatallow client device 210 and/or server device 230 to communicate. Forexample, network 240 may include a local area network (“LAN”), a widearea network (“WAN”), a metropolitan area network (“MAN”), a telephonenetwork (e.g., the Public Switched Telephone Network (“PSTN”)), an adhoc network, an intranet, the Internet, a fiber optic-based network, aprivate network, a cloud computing network, and/or a combination ofthese or other types of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example functional components of security device220. As shown in FIG. 3, security device 220 may include a SSL inboundinspection module 310, a SSL forward proxy module 320, and a servercipher preference cache 330.

SSL inbound inspection module 310 may perform operations associated withimplementing the SSL inbound inspection technique to manage encryptedtraffic associated with the SSL/TLS session. In some implementations,SSL inbound inspection module 310 may be capable of handing overmanagement of the traffic associated with the SSL/TLS session to SSLforward proxy module 320 when, for example, a Diffie-Hellman keyexchange is to be used to establish the SSL/TLS session. Additionally,or alternatively, SSL inbound inspection module 310 may include atransmission control protocol (TCP) reassemble module associated withensuring that TCP segments are received in order.

SSL forward proxy module 320 may perform operations associated withimplementing the SSL forward proxy technique to manage encrypted trafficassociated with an SSL/TLS session. In some implementations, SSL forwardproxy module 320 may be capable of receiving Diffie-Hellman parametersassociated with a Diffie-Hellman key exchange between client device 210and server device 230, such that security device 220 may generate andprovide additional Diffie-Hellman parameters to enable SSL forward proxymodule 320 to determine a session key in order to manage trafficassociated with the SSL/TLS session, as described above. Additionally,or alternatively, SSL forward proxy module 320 may include a TCP proxymodule since a TCP connection, associated with the SSL/TLS session, maybe split into two portions.

Server cipher preference cache 330 may perform functions associated withstoring server cipher preference information associated with serverdevice 230, such as information that identifies one or more key exchangeciphers supported by server device 230, priority information associatedwith the one or more key exchange ciphers supported by server device230, a server indicator associated with server device 230 (e.g., ahostname associated with server device 230, a domain name associatedwith server device 230, an IP address associated with server device 230,etc.), a virtual routing identifier corresponding server device 230, alogical system identifier corresponding to server device 230, or thelike. In some implementations, server cipher preference cache 330 may beenabled or disabled based on a configuration of security device 220. Insome implementations, server preference cipher cache 330 may locatedwithin security device 220. Additionally, or alternatively, servercipher preference cache 330 may be included in a device separate fromsecurity device 220, such as a device within a cloud computing networkthat may be accessed and/or updated by one or more security devices 220.

In some implementations, server cipher preference cache 330 may receivethe server cipher preference information from SSL forward proxy module320 and/or SSL inbound inspection module 310. For example, when SSLforward proxy module 320 is used to establish the SSL/TLS session, SSLforward proxy module 320 may receive, from server device 230, a messageassociated with initiating the SSL/TLS session, such as a server hellomessage that includes the server cipher preference information. Here,SSL forward proxy module 320 may provide the received server cipherpreference information to server cipher preference cache 330, and servercipher preference cache 330 may store the server cipher preferenceinformation accordingly (e.g., server cipher preference cache may createan entry associated with the server cipher preference information basedon a server common name included in the server certificate).Additionally, or alternatively, server cipher preference cache 330 mayreceive the server cipher preference information based on input providedby a user of security device 220.

In some implementations, server cipher preference cache 330 may receivemodified and/or updated server cipher preference information associatedwith server device 230, and may overwrite, modify, update, and/or deleteprevious server cipher preference information (e.g., server cipherpreference information received at an earlier time). For example, SSLinbound inspection module 310 may initially determine, based oninformation stored by server cipher preference cache 330, that serverdevice 230 does not support Diffie-Hellman key exchanges. In thisexample, SSL inbound inspection module 310 may continue to followmessages, associated with a SSL handshake procedure for establishing theSSL/TLS session, and may determine, (e.g., based on a server hellomessage associated with the SSL handshake procedure) updated servercipher preference information that indicates that server device 230supports Diffie-Hellman key exchanges (e.g., contrary to the initialdetermination). Here, SSL inbound inspection module 310 may provide theupdated server cipher preference information to server cipher preferencecache 330 for storage. In this example, SSL inbound inspection module310 may also hand over establishment of the SSL/TLS session and/ormanagement of the encrypted traffic to SSL forward proxy module 320.

The number and arrangement of functional components shown in FIG. 3 areprovided as an example. In practice, security device 220 may includeadditional functional components, fewer functional components, differentfunctional components, or differently arranged functional componentsthan those shown in FIG. 3. Additionally, or alternatively, a set offunctional components (e.g., one or more functional components) ofsecurity device 220 may perform one or more operations described asbeing performed by another set of functional components of securitydevice 220.

FIG. 4 is a diagram of example components of a device 400. Device 400may correspond to client device 210, security device 220, server device230, and/or server cipher preference cache 330. In some implementations,client device 210, security device 220, server device 230, and/or servercipher preference cache 330 may include one or more devices 400 and/orone or more components of device 400. As shown in FIG. 3, device 400 mayinclude a bus 410, a processor 420, a memory 430, a storage component440, an input component 450, an output component 460, and acommunication interface 470.

Bus 410 may include a component that permits communication among thecomponents of device 400. Processor 420 is implemented in hardware,firmware, or a combination of hardware and software. Processor 420 mayinclude one or more processors (e.g., a central processing unit (CPU), agraphics processing unit (GPU), an accelerated processing unit (APU),etc.), a microprocessor, and/or any processing component (e.g., afield-programmable gate array (FPGA), an application-specific integratedcircuit (ASIC), etc.) that can be programmed to perform a function.Memory 430 may include a random access memory (RAM), a read only memory(ROM), and/or another type of dynamic or static storage device (e.g., aflash memory, a magnetic memory, an optical memory, etc.) that storesinformation and/or instructions for use by processor 420.

Storage component 440 may store information and/or software related tothe operation and use of device 400. For example, storage component 440may include a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, a solid state disk, etc.), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of computer-readable medium, along with acorresponding drive.

Input component 450 may include a component that permits device 400 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, amicrophone, etc.). Additionally, or alternatively, input component 450may include a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, an actuator,etc.). Output component 460 may include a component that provides outputinformation from device 400 (e.g., a display, a speaker, one or morelight-emitting diodes (LEDs), etc.).

Communication interface 470 may include a transceiver-like component(e.g., a transceiver, a separate receiver and transmitter, etc.) thatenables device 400 to communicate with other devices, such as via awired connection, a wireless connection, or a combination of wired andwireless connections. Communication interface 470 may permit device 400to receive information from another device and/or provide information toanother device. For example, communication interface 470 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 400 may perform one or more processes described herein. Device400 may perform these processes in response to processor 420 executingsoftware instructions stored by a computer-readable medium, such asmemory 430 and/or storage component 440. A computer-readable medium isdefined herein as a non-transitory memory device. A memory deviceincludes memory space within a single physical storage device or memoryspace spread across multiple physical storage devices.

Software instructions may be read into memory 430 and/or storagecomponent 440 from another computer-readable medium or from anotherdevice via communication interface 470. When executed, softwareinstructions stored in memory 430 and/or storage component 440 may causeprocessor 420 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 4 are provided asan example. In practice, device 400 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 4. Additionally, or alternatively, aset of components (e.g., one or more components) of device 400 mayperform one or more functions described as being performed by anotherset of components of device 400.

FIG. 5 is a flow chart of an example process 500 for determining whethera Diffie-Hellman key exchange may be used to establish a secure session,and establishing the secure session accordingly. In someimplementations, one or more process blocks of FIG. 5 may be performedby security device 220. In some implementations, one or more processblocks of FIG. 5 may be performed by another device, or a group ofdevices separate from or including security device 220, such as clientdevice 210.

As shown in FIG. 5, process 500 may include receiving a messageassociated with initiating a SSL/TLS session (block 510). For example,security device 220 may receive a message associated with initiating aSSL/TLS session. In some implementations, security device 220 mayreceive the message when another device provides the message, such aswhen client device 210 provides the message.

The message may include a message associated with initiating a SSL/TLSsession via which client device 210 and server device 230 may securelyexchange information. For example, the message may include a clienthello message associated with initiating a SSL/TLS session betweenclient device 210 and server device 230.

In some implementations, the message may include client cipherinformation associated with initiating the SSL/TLS session. The clientcipher information may include information that identifies one or morekey exchange ciphers, supported by client device 210, that may be usedto establish the SSL/TLS session, such as a RSA key exchange, aDiffie-Hellman key exchange, an elliptic curve Diffie-Hellman keyexchange, or the like. Additionally, or alternatively, the client cipherinformation may include priority information associated with the one ormore key exchange ciphers. The priority information may include, forexample, information that identifies an order of priority associatedwith the one or more key exchange ciphers (e.g., when client device 210supports multiple key exchange ciphers). For example, the client cipherinformation may include priority information indicating that a firstpriority key exchange cipher for client device 210 is an elliptic curveDiffie-Hellman key exchange, that a second priority key exchange cipherfor client device 210 is a Diffie-Hellman key exchange, and that a thirdpriority key exchange cipher for client device 210 is a RSA keyexchange. Additionally, or alternatively, the client cipher informationmay include other information, such as information that identifies oneor more authentication, encryption, and/or message authentication code(MAC) algorithms associated with establishing the SSL/TLS session.

In some implementations, the message may include a server indicatorassociated with server device 230. For example, if the message is aclient hello message that conforms with transport layer security (TLS)1.0 standard or higher, the message may include a server name indication(SNI) extension that identifies a host name associated with serverdevice 230, such as a domain name, a network address, or the like. TLSprotocol and SSL protocol (discussed below) may include cryptographicprotocols designed to provide communications security over a computernetwork. Additionally, or alternatively, the message may include otherinformation associated with initiating the SSL/TLS session.

In some implementations, security device 220 may receive the messagebased on a inspecting a packet associated with the message. For example,security device 220 may be positioned between client device 210 andnetwork 240, and may be configured to inspect (e.g., using a deep packetinspection (DPI) technique) packets provided by client device 210. Here,security device 220 may, based on inspecting a packet associated withthe message, determine that the packet includes the message, and analyzethe message when, for example, security device 220 is configured toanalyze messages associated with initiating SSL/TLS sessions.

Additionally, or alternatively, security device 220 may receive and/ordetermine information for identifying a firewall rule (and an associateddecryption profile) that is to be used to manage traffic associated withthe SSL/TLS session. For example, security device 220 may receive and/ordetermine (e.g., based on the packet associated with the message) asource Internet protocol (IP) address, a destination IP address, asource port, a destination port, a transport layer protocol, or thelike, and may use some or all of this information to identify adecryption profile associated with the SSL/TLS session, as describedbelow.

As further shown in FIG. 5, process 500 may include determining thattraffic, associated with the SSL/TLS session, is to be managed using afirst decryption technique (block 520). For example, security device 220may determine that the traffic, associated with the SSL/TLS session, isto be managed using the first decryption technique. In someimplementations, security device 220 may determine that the traffic isto be managed using the first decryption technique after security device220 receives the message associated with the SSL/TLS session.Additionally, or alternatively, security device 220 may determine thatthe traffic is to be managed using the first decryption technique aftersecurity device 220 identifies a decryption profile associated with themessage, as described below.

In some implementations, security device 220 may determine that thetraffic is to be managed using the first decryption technique based on adecryption profile associated with the SSL/TLS session. The decryptionprofile may include information associated with managing, inspecting,processing, and/or monitoring encrypted traffic associated with a securesession. For example, the decryption profile may include informationthat identifies a decryption technique to be used to establish theSSL/TLS session and/or manage the encrypted traffic, such as the SSLinbound inspection technique or the SSL forward proxy technique.

In some implementations, the decryption profile may be associated withone or more firewall rules. For example, the decryption profile may beassociated with multiple firewall rules (e.g., such that the decryptionprofile is used when any of the multiple firewall rules are applied). Assuch, in some implementations, security device 220 may identify thedecryption technique based on identifying a firewall rule. For example,as described above, assume that security device 220 determines, based ona packet associated with the message, a source IP address, a destinationIP address, a source port, a destination port, a transport layerprotocol, or the like. Here, security device 220 may, based on one ormore of these items of information, identify a firewall rule to beapplied when managing, inspecting, processing, and/or monitoring trafficassociated with client device 210. In this example, security device 220may also store information that identifies a decryption profile withwhich the firewall rule is associated. Here, security device 220 mayidentify the decryption profile as the decryption profile correspondingto the firewall rule, and may determine that the SSL inbound inspectiontechnique is to be used when indicated as such by the decryptionprofile.

In some implementations, the first decryption technique may include adecryption technique to be used to establish the SSL/TLS session and/ormanage the encrypted traffic when a Diffie-Hellman key exchange is notused to establish the SSL/TLS session. In other words, the firstdecryption technique may include a decryption technique to be used whensecurity device 220 need not determine a session key, associated withthe SSL/TLS session, associated with a Diffie-Hellman key exchange. Forexample, the first decryption technique may include the SSL inboundinspection technique that causes security device 220 to determine thesession key during a RSA key exchange, and decrypt and inspect trafficwithout acting as a man-in-the-middle between client device 210 andserver device 230, as described above. In some implementations, thefirst decryption technique may be used when security device 220 storesor has access to a server certificate and a server private keyassociated with server device 230 (e.g., such that security device 220may determine the session key during a RSA key exchange). In someimplementations, use of the first decryption technique may consume fewercomputing resources than a second decryption technique (e.g., the SSLforward proxy technique). As such, it may be desirable to use the firstdecryption technique when possible.

As further shown in FIG. 5, process 500 may include determining clientcipher information included in the message (block 530). For example,security device 220 may determine client cipher information included inthe message. In some implementations, security device 220 may determinethe client cipher information after security device 220 receives themessage. Additionally, or alternatively, security device 220 maydetermines the client cipher information after security device 220determines that the encrypted traffic is to be managed using the firstdecryption technique.

As described above, in some implementations, the client cipherinformation may include information that identifies one or more keyexchange ciphers, supported by client device 210, that may be used toestablish the SSL/TLS session (e.g., a RSA key exchange, aDiffie-Hellman key exchange, an elliptic curve Diffie-Hellman keyexchange, etc.), priority information associated with the one or morekey exchange ciphers, or the like.

As further shown in FIG. 5, process 500 may include determining whetherthe client cipher information indicates a preference for using aDiffie-Hellman key exchange to establish the SSL/TLS session (block540). For example, security device 220 may determine whether the clientcipher information indicates a preference for using a Diffie-Hellman keyexchange to establish the SSL/TLS session. In some implementations,security device 220 may determine whether the client cipher informationindicates a preference for using a Diffie-Hellman key exchange aftersecurity device 220 determines the client cipher information.Additionally, or alternatively, security device 220 may determinewhether the client cipher information indicates a preference for using aDiffie-Hellman key exchange after security device 220 determines thatthe first decryption technique is to be used to manage the encryptedtraffic associated with the SSL/TLS session.

In some implementations, security device 220 may determine whether theclient cipher information indicates a preference for using aDiffie-Hellman key exchange based on the client cipher information. Forexample, the client cipher information may identify a set of keyexchange ciphers, supported by client device 210, that includes aDiffie-Hellman key exchange and a RSA key exchange. In this example, theclient cipher information may also indicate that the Diffie-Hellman keyexchange has a high priority (e.g., a level one priority, a firstpriority, etc.) and that the RSA key exchange has a low priority (e.g.,a level two priority, a second priority, etc.). In this example,security device 220 may determine that client cipher informationindicates a preference for using a Diffie-Hellman key exchange since theDiffie-Hellman key exchange cipher has a higher priority than the RSAcipher.

As another example, security device 220 may determine that the clientcipher information does not indicate a preference for using aDiffie-Hellman key exchange to establish the SSL/TLS session (e.g., whenclient device 210 does not support a Diffie-Hellman key exchange, whenclient device 210 supports only RSA key exchanges, etc.) and/or maydetermine that another type of key exchange cipher has a higher prioritythan the Diffie-Hellman key exchange cipher. Here, security device 220may determine that the client cipher information does not indicate apreference for using a Diffie-Hellman key exchange during establishmentof the SSL/TLS session.

As further shown in FIG. 5, if the client cipher information does notindicate a preference for using a Diffie-Hellman key exchange (block540—NO), then process 500 may include establishing the SSL/TLS sessionusing the first decryption technique (block 550). For example, securitydevice 220 may determine that the client cipher information does notindicate a preference for using a Diffie-Hellman key exchange toestablish the SSL/TLS session, and security device 220 may establish theSSL/TLS session using the first decryption technique.

As described above, in some implementations, the first decryptiontechnique may include a decryption technique to be used to establish theSSL/TLS session and/or manage the encrypted traffic when aDiffie-Hellman key exchange is not used to establish the SSL/TLSsession, such as the SSL inbound inspection technique to be used whensecurity device 220 stores or has access to a server certificate and aserver private key associated with server device 230. For example, theSSL inbound inspection technique may be used when a RSA key exchange isused to establish the SSL/TLS session (e.g., since security device 220may store or have access to a server private key and, thus, may decryptthe session key associated with the SSL/TLS session).

In some implementations, an amount of computing resources consumed bysecurity device 220 when using the SSL inbound inspection technique maybe less than an amount of computing resources consumed by securitydevice 220 when using the SSL forward proxy technique. As such, anamount of computing resources consumed by security device 220 may bereduced in a case when security device 220 determines that the clientcipher information does not indicate a preference for using aDiffie-Hellman key exchange and subsequently establishes the SSL/TLSsession using the SSL inbound inspection technique. Moreover, use of theSSL inbound inspection technique may result in increased SSL decryptionthroughput due to a reduced amount of processing time associated withusing the SSL inbound inspection technique.

As further shown in FIG. 5, if the client cipher information indicates apreference for using a Diffie-Hellman key exchange (block 540—YES), thenprocess 500 may include performing a server cipher preference cachelookup based on the message (block 560). For example, security device220 may determine that the client cipher information indicates apreference for using a Diffie-Hellman key exchange to establish theSSL/TLS session, and security device 220 may perform a server cipherpreference cache lookup based on the message. In some implementations,security device 220 may perform the server cipher preference cachelookup after security device 220 determines that the client cipherinformation indicates a preference for a Diffie-Hellman key exchange.

In some implementations, security device 220 may perform the servercipher preference cache lookup to determine server cipher preferenceinformation associated with server device 230. The server cipherpreference information may include information that identifies one ormore key exchange ciphers supported by server device 230 that may beused to establish the SSL/TLS session, such as a RSA key exchange, aDiffie-Hellman key exchange, an elliptic curve Diffie-Hellman keyexchange, or the like. In some implementations, the server cipherpreference information may include priority information associated withthe one or more key exchange ciphers supported by server device 230.

In some implementations, security device 220 may perform the servercipher preference cache lookup based on information included in themessage. For example, security device 220 may perform the server cipherpreference cache lookup based on the server indicator included in themessage, such as a hostname associated with server device 230 (e.g.,when security device 220 is configured to determine the hostname from aTLS SNI extension included in a client hello message). Here, securitydevice 220 may perform the server cipher preference cache lookup, basedon the server indicator, to determine whether server cipher preferencecache 330 includes an entry, associated with identifying server device230, that matches the server indicator, such as an entry that includes aserver common name that matches the server indicator and server cipherpreference information corresponding to the server common name.

In some cases, security device 220 may be capable of performing theserver cipher preference cache lookup in a virtual hosting scenarioand/or a domain name system (DNS) round robin scenario. For example,since security device 220 may perform the server cipher preference cachelookup based on the server indicator (e.g., rather than an IP addressassociated with the message), a virtual hosting scenario and/or a DNSround robin scenario that causes multiple, different IP addresses to beassociated with a server indicator may not prevent security device 220from performing the server cipher preference cache lookup.

As still another example, security device 220 may perform the servercipher preference cache lookup based on other information associatedwith the message. For example, security device 220 may perform theserver cipher preference cache lookup based on information associatedwith the message, such as a destination IP address, a destination port,a virtual routing identifier, a logical system identifier, or the like.

In some implementations, a result of the server cipher preference cachelookup may include server cipher preference information associated withthe server device 230. For example, security device 220 may determineserver cipher preference information, associated with server device 230and based on performing the server cipher preference cache lookup, thatidentifies a set of key exchange ciphers supported by server device 230.Alternatively, the result of the server cipher preference cache lookupmay indicate that server cipher preference cache 330 does not storeserver cipher preference information associated with server device 230.

As further shown in FIG. 5, process 500 may include determining, basedon a result of the server cipher preference cache lookup, whether aserver device, associated with the SSL/TLS session, supports use of aDiffie-Hellman key exchange to establish the SSL/TLS session (block570). For example, security device 220 may determine, based on theresult of the server cipher preference cache lookup, whether serverdevice 230 supports use of a Diffie-Hellman key exchange to establishthe SSL/TLS session.

In some implementations, security device 220 may determine whetherserver device 230 supports a Diffie-Hellman key exchange based on theserver cipher preference information determined as a result ofperforming the server cipher preference cache lookup. For example,security device 220 may determine, based on the server cipher preferenceinformation, that server device 230 supports a Diffie-Hellman keyexchange. As another example, security device 220 may determine, basedon the server cipher preference information, that server device 230 doesnot support a Diffie-Hellman key exchange (e.g., when server device 230is not configured to support elliptic curve Diffie-Hellman key exchangesand/or Diffie-Hellman key exchanges, when server device 230 supports useof RSA key exchanges only, when server device 230 prefers use of RSA keyexchanges over the use of Diffie-Hellman key exchanges, etc.).

Additionally, or alternatively, security device 220 may be unable todetermine whether server device 230 supports use of a Diffie-Hellman keyexchange based on the result of performing the server cipher preferencecache lookup. For example, security device 220 may determine, based onperforming the server cipher preference cache lookup, that server cipherpreference cache 330 does not store server cipher preference informationassociated with server device 230, and security device 220 may be unableto determine whether server device 230 supports a Diffie-Hellman keyexchange.

As further shown in FIG. 5, if the server device, associated with theSSL/TLS session, does not support use a Diffie-Hellman key exchange(block 570—NO), then process 500 may include establishing the SSL/TLSsession using the first decryption technique (block 550). For example,security device 220 may determine that the server device, associatedwith the SSL/TLS session, does not support use of a Diffie-Hellman keyexchange to establish the SSL/TLS session, and security device 220 mayestablish the SSL/TLS session using the first decryption technique, asdescribed above with regard to block 550.

As further shown in FIG. 5, if the server device, associated with theSSL/TLS session, supports use a Diffie-Hellman key exchange, or if it isunknown whether the server device supports use of a Diffie-Hellman keyexchange (block 570—YES/UNKNOWN), then process 500 may includeestablishing the SSL/TLS session using a second decryption technique(block 580). For example, security device 220 may determine that serverdevice 230, associated with the SSL/TLS session, supports use of aDiffie-Hellman key exchange to establish the SSL/TLS session, andsecurity device 220 may establish the SSL/TLS session using the seconddecryption technique. As another example, security device 220 may beunable to determine whether server device 230, associated with theSSL/TLS session, supports use of a Diffie-Hellman key exchange, andsecurity device 220 may establish the SSL/TLS session using the seconddecryption technique.

The second decryption technique may include a decryption technique to beused to establish the SSL/TLS session and/or manage the encryptedtraffic when a Diffie-Hellman key exchange may be used to establish theSSL/TLS session. In other words, the second decryption technique mayinclude a decryption technique to be used when security device 220 mayneed to intervene in a Diffie-Hellman key exchange in order to determinea session key associated with the SSL/TLS session, in the mannerdescribed above. For example, the second decryption technique mayinclude the SSL forward proxy technique that causes security device 220to create two Diffie-Hellman key exchanges associated with establishingthe SSL/TLS session, as described above. By acting as aman-in-the-middle between client device 210 and server device 230 duringthe Diffie-Hellman key exchange, security device 220 may be capable ofdetermining the session key, which may allow security device 220 tomanage encrypted traffic associated with the SSL/TLS session.

By intelligently determining when the second decryption technique is tobe used based on whether the SSL/TLS session may be established using aDiffie-Hellman key exchange, security device 220 may be capable ofmanaging the encrypted traffic, associated with a SSL/TLS session, evenwhen a Diffie-Hellman key exchange is used to establish the SSL/TLSsession, rather than dropping the SSL/TLS session or allowing thetraffic to pass security device 220 without being inspected.

In some implementations, security device 220 may establish the SSL/TLSsession using the determined decryption technique, and may update servercipher preference cache 330 based on information received duringestablishment of the SSL/TLS session. For example, assume that securitydevice 220 determines that server cipher preference cache 330 does notstore server cipher preference information associated with server device230, and that the SSL/TLS session is established using the SSL forwardproxy technique. Here, security device 220 may receive (e.g., in aserver hello message provided by server device 230) server cipherpreference information, associated with establishing the SSL/TLSsession, indicating that server device 230 does not support use ofDiffie-Hellman key exchanges, and may update server cipher preferencecache 330 accordingly. As such, for a next SSL/TLS session with serverdevice 230, security device 220 may be capable of determining thatserver device 230 does not support use of Diffie-Hellman key exchanges,and may use the SSL inbound inspection technique to establish theSSL/TLS session in the manner described above.

Additionally, or alternatively, server cipher preference information,received from server device 230 during establishment of the SSL/TLSsession may differ from the server cipher preference information storedby server cipher preference cache. For example, assume that securitydevice 220 determines that the SSL inbound inspection technique is to beused to establish the SSL and manage the traffic associated with theSSL/TLS session. Further, assume that security device 220 receives,during establishment of the SSL/TLS session, a server hello message thatincludes server cipher preference information indicating that serverdevice 230 supports and/or prefers the use of a Diffie-Hellman keyexchange to establish the SSL/TLS session. In this example, SSL inboundinspection module 310 may hand over establishment of the SSL/TLS sessionto SSL forward proxy module 320, and SSL forward proxy module 320 maygenerate its own server hello message with Diffie-Hellman parameters forprovision to client device 210. Here, SSL forward proxy module 320 mayuse server generated Diffie-Hellman parameters (e.g., provided in theserver hello message) for the Diffie-Hellman key exchange with serverdevice 230, and may proceed with establishing the SSL/TLS session usingthe SSL forward proxy technique, as described above.

Although FIG. 5 shows example blocks of process 500, in someimplementations, process 500 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 5. Additionally, or alternatively, two or more of theblocks of process 500 may be performed in parallel.

FIG. 6 is a diagram of an example implementation 600 relating to exampleprocess 500 shown in FIG. 5. For the purposes of example implementation600, assume that security device 220 is positioned between client device210 and server device 230, and that security device 220 hosts a firewallassociated with managing, inspecting, processing, monitoring, or thelike, traffic provided by and/or destined for client device 210.

As shown in FIG. 6, and by reference number 610, client device 210 mayreceive an indication to initiate a SSL/TLS session with server device230. As shown by reference number 620, client device 210 may provide aSSL client hello message associated with initiating the SSL/TLS sessionwith server device 230. As shown, the SSL client hello message mayinclude client cipher information identifying a Diffie-Hellman keyexchange cipher as a preferred cipher associated with establishing theSSL/TLS session, a SNI associated with server device 230, and otherinformation associated with establishing the SSL/TLS session.

For the purposes of FIG. 6, assume that security device 220 isconfigured to inspect traffic provided by client device 210, and analyzemessages associated with initiating SSL/TLS sessions provided by clientdevice 210. After analyzing the client hello message, security device220 may (e.g., based on information included in a packet associated withthe message) identify a firewall rule, and may determine a decryptionprofile associated with the firewall rule. As shown by reference number630, assume that the decryption profile indicates that security device220 is to use SSL inbound inspection to manage traffic for the SSL/TLSsession initiated by client device 210.

As shown by reference number 640, SSL inbound inspection module 310 maydetermine, based on the client cipher information included in the clienthello message, that client device 210 has indicated a preference to usea Diffie-Hellman key exchange to establish the SSL/TLS session. As shownby reference number 650, after determining that client device 210 hasindicated the preference for the Diffie-Hellman key exchange, securitydevice 220 may perform a server cipher preference cache lookup using theserver indicator included in the client hello message. As shown byreference number 660, a result of the server cipher preference cachelookup may indicate that server device 230 supports use ofDiffie-Hellman key exchanges to establish SSL/TLS sessions. As shown byreference number 670, based on determining that server device 230supports a Diffie-Hellman key exchange, SSL inbound inspection module310 may hand over establishment of the SSL/TLS session and management ofencrypted traffic, associated with the SSL/TLS session, to SSL forwardproxy module 320 in order to allow SSL forward proxy module 320 toestablish the SSL/TLS session using the SSL forward proxy technique. Asshown by reference number 680, SSL forward proxy module 320 may proceedwith establishing the SSL/TLS session in the manner described above, andmay subsequently manage the encrypted traffic for the SSL/TLS sessionusing the SSL forward proxy technique (e.g., after determining a sessionkey associated with the SSL/TLS session due to implementing the SSLforward proxy technique to intervene in the Diffie-Hellman keyexchange).

As indicated above, FIG. 6 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 6.

FIG. 7 is a diagram of an additional example implementation 700 relatingto example process 500 shown in FIG. 5. For the purposes of exampleimplementation 700, assume that security device 220 is positionedbetween client device 210 and server device 230, and that securitydevice 220 hosts a firewall associated with managing, inspecting,processing, monitoring, or the like, traffic provided by and/or destinedfor client device 210.

As shown in FIG. 7, and by reference number 710, client device 210 mayreceive an indication to initiate a SSL/TLS session with server device230. As shown by reference number 720, client device 210 may provide aSSL client hello message associated with initiating the SSL/TLS sessionwith server device 230. As shown, the SSL client hello message mayinclude client cipher information identifying a Diffie-Hellman keyexchange cipher as a preferred cipher associated with establishing theSSL/TLS session, a SNI associated with server device 230, and otherinformation associated with establishing the SSL/TLS session.

For the purposes of FIG. 7, assume that security device 220 isconfigured to inspect traffic provided by client device 210, and analyzemessages associated with initiating SSL/TLS sessions provided by clientdevice 210. After analyzing the client hello message, security device220 may (e.g., based on information included in a packet associated withthe message) identify a firewall rule, and may determine a decryptionprofile associated with the firewall rule. As shown by reference number730, assume that the decryption profile indicates that security device220 is to use SSL inbound inspection to establish the SSL/TLS sessionand manage encrypted traffic associated with the SSL/TLS sessioninitiated by client device 210.

As shown by reference number 740, SSL inbound inspection module 310 maydetermine, based on the client cipher information included in the clienthello message, that client device 210 has indicated a preference to usea Diffie-Hellman key exchange to establish the SSL/TLS session. As shownby reference number 750, after determining that client device 210 hasindicated the preference for the Diffie-Hellman key exchange, securitydevice 220 may perform a server cipher preference cache lookup using theserver indicator included in the client hello message. As shown byreference number 760, a result of the server cipher preference cachelookup may indicate that server device 230 does not support use of aDiffie-Hellman key exchange to establish SSL/TLS sessions (e.g., thatserver device 230 prefers RSA key exchanges, that server device 230supports RSA key exchanges only). As shown by reference number 770,based on determining that server device 230 does not support use aDiffie-Hellman key exchange and, as shown by reference number 780, SSLinbound inspection module 310 may proceed with establishing the SSL/TLSsession (e.g., using a RSA key exchange, a server certificate associatedwith server device 230, a server private key associated with serverdevice 230, etc.). SSL inbound inspection module 310 may proceed withmanaging the SSL/TLS session using the SSL inbound inspection techniqueafter the SSL/TLS session is established.

As indicated above, FIG. 7 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 7.

FIG. 8 is a diagram of an additional example implementation 800 relatingto example process 500 shown in FIG. 5. For the purposes of exampleimplementation 800, assume that security device 220 is positionedbetween client device 210 and server device 230, and that securitydevice 220 hosts a firewall associated with managing, inspecting,processing, monitoring, or the like, traffic provided by and/or destinedfor client device 210.

As shown in FIG. 8, and by reference number 810, client device 210 mayreceive an indication to initiate a SSL/TLS session with server device230. As shown by reference number 820, client device 210 may provide aSSL client hello message associated with initiating the SSL/TLS sessionwith server device 230. As shown, the SSL client hello message mayinclude client cipher information identifying a Diffie-Hellman keyexchange cipher as a preferred cipher associated with establishing theSSL/TLS session, a SNI associated with server device 230, and otherinformation associated with establishing the SSL/TLS session.

For the purposes of FIG. 8, assume that security device 220 isconfigured to inspect traffic provided by client device 210, and analyzemessages associated with initiating SSL/TLS sessions provided by clientdevice 210. After analyzing the client hello message, security device220 may (e.g., based on information included in a packet associated withthe message) identify a firewall rule, and may determine a decryptionprofile associated with the firewall rule. As shown by reference number830, assume that the decryption profile indicates that security device220 is to use SSL inbound inspection to manage traffic for the SSL/TLSsession initiated by client device 210.

As shown by reference number 840, SSL inbound inspection module 310 maydetermine, based on the client cipher information included in the clienthello message, that client device 210 has indicated a preference to usea Diffie-Hellman key exchange to establish the SSL/TLS session. As shownby reference number 850, after determining that client device 210 hasindicated the preference for the Diffie-Hellman key exchange, securitydevice 220 may perform a server cipher preference cache lookup using theserver indicator included in the client hello message. As shown byreference number 860, a result of the server cipher preference cachelookup may indicate that security device 220 does not store or haveaccess to server cipher preference information associated with serverdevice 230 (i.e., that it is unknown whether server device 230 supportsuse of a Diffie-Hellman key exchange).

As shown by reference number 870, based on determining that it isunknown whether server device 230 supports a Diffie-Hellman keyexchange, SSL inbound inspection module 310 may hand over establishmentof the SSL/TLS session and management of encrypted traffic, associatedwith the SSL/TLS session, to SSL forward proxy module 320. As shown byreference number 880, SSL forward proxy module 320 may proceed withestablishing the SSL/TLS session using the SSL forward proxy technique.For example, SSL forward proxy module 320 may determine, based on aserver hello message, whether server device 230 supports aDiffie-Hellman key exchange, and may establish the SSL/TLS sessionaccordingly. In this example, as shown by reference number 890, securitydevice 220 may also store server cipher preference information (e.g.,create a server cipher cache entry), determined based on the serverhello message, for future use in determining whether server device 230supports use of a Diffie-Hellman key exchange. Security device 220 maythen manage encrypted traffic for the SSL/TLS session using the SSLforward proxy technique.

As indicated above, FIG. 8 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 8.

Implementations described herein may allow a security device todetermine when a secure session is to be established using aDiffie-Hellman key exchange and, based on the determination, identify adecryption technique to be used when establishing and managing thesecure session. In this way, the security device may implement a firstdecryption technique (e.g., the SSL inbound inspection technique) whenpossible, which may lead to increased SSL decryption throughput ascompared to implementing a second decryption technique (e.g., the SSLforward proxy technique).

Moreover, in some implementations, use of the SSL forward proxytechnique may result in splitting of a TCP connection associated with aSSL/TLS session after receiving a packet associated with the TCPconnection. Such dynamic engagement of a TCP proxy technique (e.g., onan as-needed basis) may result in benefits associated with managing theTCP connection and/or in other scenarios unrelated to SSL.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, and/or a combination of hardware and software.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the terms “group” and “set” are intended to include oneor more items (e.g., related items, unrelated items, a combination ofrelated items and unrelated items, etc.), and may be usedinterchangeably with “one or more.” Where only one item is intended, theterm “one” or similar language is used. Also, as used herein, the terms“has,” “have,” “having,” or the like are intended to be open-endedterms. Further, the phrase “based on” is intended to mean “based, atleast in part, on” unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: receiving, by a device,client cipher information associated with initiating a secure session,the client cipher information identifying one or more key exchangeciphers supported by a client device associated with the secure session;determining, by the device and based on the client cipher information,that the client device prefers use of a Diffie-Hellman key exchange toestablish the secure session; determining, by the device, whether aserver device, associated with the secure session, supports the use ofthe Diffie-Hellman key exchange to establish the secure session; andselectively establishing, by the device, the secure session using afirst decryption technique or a second decryption technique based ondetermining whether the server device supports the use of theDiffie-Hellman key exchange, the first decryption technique beingdifferent from the second decryption technique.
 2. The method of claim1, comprising: receiving a message associated with initiating the securesession, the message including the client cipher information; and wherereceiving the client cipher information comprises: receiving the clientcipher information based on receiving the message associated withinitiating the secure session.
 3. The method of claim 1, wheredetermining whether the server device supports the use of theDiffie-Hellman key exchange comprises: receiving server cipherpreference information associated with the server device, the servercipher preference information including information indicating whetherthe server device supports the use of the Diffie-Hellman key exchange;and determining whether the server device supports the use of theDiffie-Hellman key exchange based on the received server cipherpreference information.
 4. The method of claim 1, further comprising:determining that traffic, associated with the secure session, is to bemanaged using the first decryption technique; and determining, based ondetermining that the server device does not support the use of theDiffie-Hellman key exchange, that the traffic is to be managed using thesecond decryption technique rather than the first decryption technique.5. The method of claim 1, where the first decryption technique is asecure sockets layer (SSL) forward proxy technique and the seconddecryption technique is a SSL inbound inspection technique.
 6. Themethod of claim 1, where determining whether the server device supportsthe use of the Diffie-Hellman key exchange comprises: determining, basedon a message associated with initiating the secure session, a serverindicator associated with the server device; performing a lookup basedon the server indicator; and determining whether the server devicesupports the use of the Diffie-Hellman key exchange based on a result ofthe lookup.
 7. The method of claim 1, where the secure session is asecure sockets layer (SSL) session or a transport layer security (TLS)session.
 8. A device, comprising: one or more processors to: receiveclient cipher information associated with initiating a secure session,the client cipher information identifying at least one key exchangecipher supported by a client device associated with the secure session;determine, based on the client cipher information, that a Diffie-Hellmankey exchange is to be used to establish the secure session; determinewhether a server device, associated with the secure session, supportsuse of the Diffie-Hellman key exchange to establish the secure session;and manage establishment of the secure session using a first decryptiontechnique based on determining that the server device does not supportthe use of the Diffie-Hellman key exchange; manage establishment of thesecure session using a second decryption technique based on determiningthat the server device supports the use of the Diffie-Hellman keyexchange; or manage establishment of the secure session using the seconddecryption technique based on being unable to determine whether theserver device supports the use of the Diffie-Hellman key exchange. 9.The device of claim 8, where the one or more processors, whendetermining that the Diffie-Hellman key exchange is to be used toestablish the secure session, are to: determine, based on the clientcipher information, priority information associated with the at least onkey exchange cipher supported by the client device; and determine thatthe Diffie-Hellman key exchange is to be used based on the priorityinformation.
 10. The device of claim 8, where the one or more processorsare to: receive a message associated with initiating the secure session,the message including the client cipher information; and where the oneor more processors, when receiving the client cipher information, areto: receive the client cipher information based on receiving the messageassociated with initiating the secure session.
 11. The device of claim8, where the one or more processors, when determining whether the serverdevice supports the use of the Diffie-Hellman key exchange, are to:store server cipher preference information associated with the serverdevice, the server cipher preference information including informationindicating whether the server device supports the use of theDiffie-Hellman key exchange; and determine whether the server devicesupports the use of the Diffie-Hellman key exchange based on the storedserver cipher preference information.
 12. The device of claim 8, wherethe one or more processors are to: determine that traffic, associatedwith the secure session, is to be managed using the first decryptiontechnique; and determine, based on determining that the server devicedoes not support the use of the Diffie-Hellman key exchange, that thetraffic is to be managed using the second decryption technique ratherthan the first decryption technique.
 13. The device of claim 8, wherethe Diffie-Hellman key exchange is an elliptic curve Diffie-Hellman keyexchange.
 14. The device of claim 8, where the one or more processors,when determining whether the server device supports the use of theDiffie-Hellman key exchange, are to: determine a server indicatorassociated with the server device; perform a lookup based on the serverindicator; and determine whether the server device supports the use ofthe Diffie-Hellman key exchange based on a result of the lookup.
 15. Acomputer-readable medium storing instructions, the instructionscomprising: one or more instructions that, when executed by one or moreprocessors, cause the one or more processors to: receive client cipherinformation associated with initiating a secure sockets layer session ora transport layer security session (SSL/TLS session), the client cipherinformation identifying a set of key exchange ciphers supported by aclient device associated with the SSL/TLS session; determine, based onthe client cipher information, that a Diffie-Hellman key exchange is tobe used to establish of the SSL/TLS session; determine whether a serverdevice, associated with the SSL/TLS session, supports use of theDiffie-Hellman key exchange to establish of the SSL/TLS session; andestablish the SSL/TLS session using a SSL forward proxy technique basedon determining that the server device supports the use of theDiffie-Hellman key exchange or based on being unable to determinewhether the server device supports the use of the Diffie-Hellman keyexchange; or establish the SSL/TLS session using a SSL inboundinspection technique based on determining that the server device doesnot support the use of the Diffie-Hellman key exchange.
 16. Thecomputer-readable medium of claim 15, where the one or moreinstructions, that cause the one or more processors to determine thatthe Diffie-Hellman key exchange is to be used to establish of theSSL/TLS session, cause the one or more processors to: determine, basedon the client cipher information, priority information associated withthe set of key exchange ciphers supported by the client device; anddetermine, based on the priority information, that the Diffie-Hellmankey exchange is to be used to establish of the SSL/TLS session.
 17. Thecomputer-readable medium of claim 15, where the one or moreinstructions, after causing the one or more processors to determine thatthe SSL inbound inspection technique is to be used to establish of theSSL/TLS session based on determining that the server device does notsupport the use of the Diffie-Hellman key exchange, further cause theone or more processors to: receive a server hello message associatedwith initiating the SSL/TLS session, the server hello message indicatingthat the server device supports the use of the Diffie-Hellman keyexchange; and establish the SSL/TLS session, using the SSL forward proxytechnique, based on the server hello message indicating that the serverdevice supports the use of the Diffie-Hellman key exchange.
 18. Thecomputer-readable medium of claim 15, where the one or moreinstructions, when executed by the one or more processors, further causethe one or more processors to: receive a client hello message associatedwith initiating the SSL/TLS session, the client hello message includingthe client cipher information; and where the one or more instructions,that cause the one or more processors to receive the client cipherinformation, cause the one or more processors to: receive the clientcipher information based on receiving the client hello messageassociated with initiating the SSL/TLS session.
 19. Thecomputer-readable medium of claim 15, where the one or moreinstructions, that cause the one or more processors to determine whetherthe server device supports the use of the Diffie-Hellman key exchange,cause the one or more processors to: store server cipher preferenceinformation associated with the server device, the server cipherpreference information including information indicating whether theserver device supports the use of the Diffie-Hellman key exchange; anddetermine whether the server device supports the use of theDiffie-Hellman key exchange based on the stored server cipher preferenceinformation.
 20. The computer-readable medium of claim 15, where the oneor more instructions, that cause the one or more processors to determinewhether the server device supports the use of the Diffie-Hellman keyexchange, cause the one or more processors to: determine a serverindicator associated with the server device; perform a lookup based onthe server indicator; and determine whether the server device supportsthe use of the Diffie-Hellman key exchange based on a result of thelookup.